Task completion

ABSTRACT

The concepts relate to task completion and specifically to aiding a user to complete an unfinished task at a subsequent time and/or on another device. One example can identify that a user is working on a task on a computing device associated with the user. In an instance when the user stops using the computing device without completing the task, the example can predict a likelihood that the user will subsequently resume the task on a second computing device associated with the user. In an instance where the likelihood exceeds a threshold, the example can attempt to aid the user in completing the task on the second computing device.

BACKGROUND

Users often utilize computers to accomplish tasks, such as search tasks or document completion tasks. In many cases, the user starts and completes the tasks in a given computing scenario. However, in other cases, the user is unable to complete the task in the given computing scenario. The present description relates to aiding the users in the latter cases.

SUMMARY

The described implementations relate to task completion. In some cases a user can work on a task on a computing device associated with the user. The user may stop using the computing device without completing the task. In such a case, one application can predict that the user will subsequently resume the task on a second computing device associated with the user. The application can cause the task to be automatically presented to the user on the second computing device. The application can further predict actions that the user will take to complete the task. The further prediction can be based upon user interactions on prior tasks. The application can take individual actions on behalf of the user to assist the user in completing the task.

The above listed example is intended to provide a quick reference to aid the reader and is not intended to define the scope of the concepts described herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate implementations of the concepts conveyed in the present document. Features of the illustrated implementations can be more readily understood by reference to the following description taken in conjunction with the accompanying drawings. Like reference numbers in the various drawings are used wherever feasible to indicate like elements. Further, the left-most numeral of each reference number conveys the FIG. and associated discussion where the reference number is first introduced.

FIGS. 1-3 show examples of systems configured to aid in task completion in accordance with some implementations of the present concepts.

FIGS. 4-6 show examples of devices configured to aid in task completion in accordance with some implementations of the present concepts.

FIGS. 7-8 are flowcharts of examples of task completion techniques in accordance with some implementations of the present concepts.

DETAILED DESCRIPTION Overview

This patent relates to assisting a user to complete a task. For introductory purposes, consider FIG. 1 which shows a task assistance system 100. The system 100 relates to a user 102. The user works on a task 104 as indicated by arrow 106. At this point, the user is working on task 104 on computing device 108(1). In this instance, the user stops working on the task at point 110. At 112, the system can make a determination whether the user will resume the task. In some cases, the user can provide an express indication that the user will resume the task. For instance, the user could select an icon that says ‘task incomplete—will resume later’. In other cases, the user may not provide any indication whether he or she will resume the task. In these cases, the determination can entail a prediction whether the user is likely to resume the task. The system can utilize various factors or parameters to generate the prediction. Briefly, the parameters can relate to previous user actions, time, etc. Examples of such parameters are described below relative to FIG. 2.

If a determination is made that the user is likely to resume the task, the system can aid the user in completing the task. For instance, the system can expend resources on behalf of the user to have results waiting for the user on resumption of the task. Other ways in which the user can be aided in completing the task are described below relative to FIG. 2 and FIGS. 4-6.

At point 114, the user can resume the task on device 108(1) as indicated by arrow 116 or on device 108(2) as indicated by arrow 118. The user can complete the task at 120. The present concepts can make it easier for the user to complete the task than would otherwise be the case.

FIG. 2 shows another task assistance system 200 that includes a first computing device 202(1) and second computing device 202(2). Task assistance system 200 also includes a cross-device task continuation predictor 204, a proactive tool 206, and a task synthesizer 208. This system 200 relates to a specific scenario introduced in FIG. 1. This scenario involves a user utilizing first computing device 202(1) to start a task and second computing device 202(2) to finish the task. In this example, the task is a web search task. In this case, the first computing device can be manifest as a notebook or desktop computer. The second computing device 202(2) can be manifest as a smart phone or other computing device.

The user engages in the web search task in first session 210 on the first computing device 202(1). The user may resume the web search task on second computing device 202(2). In this example, the first computing device 202(1) can have a relatively large user display when compared to the second computing device 202(2). In other implementations, the display areas of the first and second computing devices may be equal, or the second computing device may have a larger display area. Of course, while relative screen size is discussed here, the computing devices may have differences in other device capabilities, such as processing power, memory/storage, network bandwidth, input devices, etc.

In the illustrated case, during the desktop session 210, the user works on the task as indicated by line 212. The user terminates the task at point 214 without completing the task. The user may or may not resume (designator 216) the task during a subsequent second or mobile session 218 on the second computing device 202(2). If the user does resume the task at 216, progress on the task is represented on line 219. The task assistance system 200 can utilize various prediction parameters to try to predict whether the user will resume the task. In the event that the prediction indicates that the user is likely to resume the task, the task assistance system 200 can take various actions to aid the user. These two aspects are discussed below. Note that the functionality provided by task assistance system 200 can involve multiple parallel dynamic feedback loops. As such, the order in which the components and processes are introduced is somewhat arbitrary and the system can be better appreciated at the conclusion of the description.

Some prediction parameters can relate to the first session (e.g., desktop session) 210. For instance the parameter can include search interactions, queries, and search engine results page (SERP) clicks 220 between the user and a search engine 222. Another prediction parameter can relate to results 224 provided by the search engine 222 responsive to the search interactions, queries and SERP clicks 220. These prediction parameters can be sent to cross-device task continuation predictor 204 as indicated at 226. The performance of the cross-device task continuation predictor 204 can be enhanced in some implementations through the use of off-line training as indicated at 228. A pre-switch prediction 230 can relate to a likelihood that the user will resume the search on the second computing device 202(2). Briefly, the pre-switch prediction 230 can be a binary prediction (e.g., true/false) or a percent likelihood (e.g., weighted determination). The cross-device task continuation predictor 204 can also make a post switch prediction 231. Pre and post switch predictions are described below.

The pre-switch prediction 230 can also be supplied to proactive tool 206 as indicated at 232. The proactive tool 206 can include a proactive search engine support state saver, a reconnaissance agent, and/or a search quality amplifier, among others. The proactive tool 206 can also receive input from previous user interactions 234 with computing device 202(1) (and/or other computing devices). In this example, the previous user interactions 234 can include a search state from pre-switch session 236. The search state from pre-switch session 236 can be supplied to the proactive tool as indicated at 238.

The proactive tool 206 can use the pre-switch prediction 230, the search state from pre-switch sessions 236, and/or alerts 240, among others, as input parameters. The proactive tool can determine a selected support action (e.g., selected support 242) to take based upon the input parameters. If the selected support utilizes the state of the first computing device 202(1) (e.g., desktop computer device) then the proactive tool 206 can cause the state to be saved. In the illustrated case, a save state condition is true at 244. As such, the proactive tool can save the task state (in this case the search state at 246). The saved search state 246 and the selected support 242 can be supplied to task synthesizer 208 as indicated at 248 and 250, respectively.

The task synthesizer 208 can utilize the saved search state 246 and the selected support 242 to prepare for user resumption of the search task (resume 216). For example, task synthesizer 208 can access search engine 222 as indicated at 252. The task synthesizer can refine the user search and/or expend other resources on behalf of the user to speed up the user's subsequent search, make the search easier, and/or make the search more productive.

Now that the elements of task assistance system 200 have been introduced another explanation is provided below. Viewed from one perspective, system 200 shows an architecture block diagram of the cross-device support for desktop to mobile prediction. In the example, the user starts their task on the first computing device 202(1) (e.g., desktop PC) as indicated by line 212. Subsequently, the user terminates (at 214) the task on the first computing device and resumes (at 216) the task on his/her second computing device 202(2) (e.g., mobile device) as indicated by line 219.

The cross-device task continuation predictor 204 can make various predictions relating to whether the user will resume the task. The continuation predictor can make the predictions at any point between task termination and task resumption. In the illustrated configuration the continuation predictor makes predictions at two points. The first point is immediately (shortly) after the user stops searching on his/her first computing device 202(1) (e.g., once the user closes the browser or logs-off the machine). This is termed the pre-switch prediction 230. The second point occurs once the user starts to search on the second computing device 202(2) by visiting the search engine homepage (e.g., post-switch prediction 231). The cross-device task continuation predictor 204 can pass its prediction (binary or weighted) plus optionally, the features and their weights, to the proactive tool 206. As noted above, the predictions are not limited to the types of predictions and/or points in time at which the predictions occur in the illustrated example.

The proactive tool 206 can decide what action to perform. In some cases, a single action can be performed. In other cases, the proactive tool 206 could decide between a set of actions based on the classifier confidence and the feature weights. This could be a machine-learned model or weights/rules could be set manually by search engine designers. If the selected action entails future access to the user's search state, then the search state can be committed to a data store (memory or disk-based) 246. When the user starts searching on the post-switch device (e.g., the second computing device 202(2)), the task synthesizer 208 can take the selected support and the state if utilized, and can determine what the search engine should do. For instance, the task synthesizer 208 could decide to add links/buttons to a homepage, bias autocomplete suggestions, incorporate results found by the system 200 during the background (between-devices) searching, etc. The task assistance system 200 can also show alerts 240 to the user on the second computing device 202(2) during the downtime between search sessions. The alerts 240 can provide the user with real-time updates on search progress. The alerts can also prompt the user to return to the search engine earlier than may otherwise be the case.

Note that information about the computing devices can also be useful in determining how to help the user. For instance, a desktop to mobile device switch can have different ramifications than a mobile device to desktop switch. For example, in many cases, desktop to mobile device switches are induced by time constraints (e.g., the user has to go somewhere and cannot take the desktop with them and so the user switches to the mobile device). In that case, the mobile device tends to have much less screen space and a more rudimentary input device. As such, prepopulating content to reduce user input on the mobile device can be very valuable to the user. Further, using location and/or direction of travel information (among others) from the mobile device can provide a valuable filter for the results so that user entry and selection on the mobile device is further reduced. For example, assume that the user entered “hit movies” on the desktop and then had to leave before finishing the search task.

The cross-device task continuation predictor 204 can make a prediction that the user is likely to resume the task on another (e.g., second) computing device 202(2). The proactive tool 206 can start to refine the search for the user based upon past user interactions. For example, the proactive tool may refine the search to find movie theaters playing hit movies. Once the user starts to utilize the mobile device, the proactive tool can further refine the search to find the movie theaters that are close to the location of the mobile device and emphasize those movie theaters that are in the direction that the user is moving with the mobile device. For instance, if the user is moving North with the mobile device, such as in a car or bus, the proactive tool can use this information to present a movie theater that is five miles to the North of the user over another movie theater that is five miles to the South of the user. In the opposite scenario where the user switches from the mobile device to the desktop, the user may be switching because they are in proximity of their desktop and can utilize its (potentially) superior user interface and input devices. In such a case, the proactive tool may re-establish the state of the user search on the mobile device so that the user can immediately resume the search task on the desktop.

Further, the proactive tool 206 can utilize the previous user interactions 234 to determine which types of tasks the user is likely to resume when switching in each direction. For instance, the user may be likely to resume an email task when switching both ways, desktop to mobile device or mobile device to desktop. However, the user may be likely to resume a document creation task when switching from mobile device to desktop to take advantage of the display area and input devices of the desktop. However, the user may not be likely to resume the document creation when switching from desktop to mobile device. Instead, past experience could indicate that the user waits until getting back to the desktop. Alternatively, the user may not tend to resume the document creation task on the mobile device, but may tend to resume once the user gets to their office on his/her work computer. As such, the task resumption concepts can involve more than two devices.

Task resumption may not go from device to device in a serial fashion or it may skip devices. In the above example, the user may not finish the document creation task on their home desktop, and may use their mobile device on the bus ride to work, but may not resume the document creation task until they log on to their work computer. The present concepts can make such a prediction. In that case, the proactive tool 206 may not take any action to present the document on the mobile device, but may present the document to the user upon login to their work computer.

Cross-device task continuation predictor 204 can utilize predictive models to make its predictions 230 and 231. The predictive models can leverage behavioral, topical, geospatial, and/or temporal features, among others derived from the current user's search history and/or in the aggregate across all searchers.

The post-switch prediction 231 can be investigated in an instance where the user does in fact resume the task on the post switch device. For example, once the user visits the homepage of the search engine on the second computing device 202(2), cross-device task continuation predictor 204 can predict that the user is going to resume the last task attempted on the first computing device 202(1). Some implementations can make post-switch predictions 231 at two points. The first point can occur when the user visits the search engine homepage on the second computing device 202(2). The second point can occur once the user has entered the first query on the second computing device (but before providing the results).

The proactive tool 206 can identify candidate features for the predictive models by characterizing existing cross-device task transitions utilizing the previous user interactions 234. For example, the proactive tool can identify patterns in device transitions and explore the temporal, geospatial, and topical aspects of cross-device searching.

The task synthesizer 208 can leverage the predictions of task resumption to help searchers perform cross-device searching at different points in the device switch. Search engines can offer help at two particular points, among others. The first point can occur immediately following the session on the pre-switch device (e.g., proactively retrieve task-relevant content). The second point can occur upon the user visiting the search engine homepage on the post-switch device (e.g., provide users with the option to resume their previous task).

In summary, web searchers frequently transition from desktop computers and laptops to mobile devices, and vice versa. Little support is provided for cross-device search tasks, yet they represent a potentially important opportunity for search engines to help their users, especially those on the target (post-switch) device. If the cross-device task communication predictor 204 can predict in advance that the user is going to resume their current search task on a different device with the next query, it could offer a range of support to help users resume their task on the post-switch device. For example, the proactive tool 206 could save the current session and re-instate it after the switch (e.g., show previous searches on the search engine homepage on the post-switch device. Alternatively or additionally, the proactive tool 206 could leverage pre-switch behavior as search context for queries issued on the post-switch device). In still another case, the proactive tool 206 could capitalize on down-time between devices to proactively retrieve novel or more relevant content on behalf of the searcher in the background while they are engaged in other tasks such as walking to the bus stop, where they will then resume their search task.

Note that while FIG. 2 explains in detail a scenario where the user task involves a search task, the concepts can be applied to other types of user tasks.

FIG. 3 shows another system 300 that can enable the task assistance concepts described above. Further, system 300 can include multiple devices 302. In this case, device 302(1) is manifest as a smart phone and device 302(2) is manifest as a tablet type computer. Similarly, device 302(3) is manifest as a notebook computer, device 302(4) is manifest as an entertainment device, and device 302(5) is manifest as server computer, such as a cloud based server computer. (In this discussion, the use of a designator with the suffix, such as “(1)”, is intended to refer to a specific device instance. In contrast, use of the designator without a suffix is intended to be generic). Of course, not all device implementations can be illustrated and other device implementations should be apparent to the skilled artisan from the description above and below.

Devices 302 can communicate over one or more networks represented by lightning bolts 304. The devices 302 can include several elements which are defined below. For example, these devices can include a processor 306, storage/memory 308, and/or a task completion component 310. The task completion component 310 can include cross-device task continuation predictor 204, proactive tool 206, and/or task synthesizer 208. The devices 302 can alternatively or additionally include other elements, such as input/output devices (e.g., touch, voice, and/or gesture), buses, graphics cards, wireless circuitry, cellular circuitry, GPS circuitry, etc., which are not illustrated or discussed here for sake of brevity.

In some configurations, task completion component 310 can be installed as hardware, firmware, or software during manufacture of the device 302 or by an intermediary that prepares the device for sale to the end user. In other instances, the end user may install the task completion component 310, such as in the form of a downloadable application.

The term “device”, “computer”, or “computing device” as used herein can mean any type of device that has some amount of processing capability and/or storage capability. Processing capability can be provided by one or more processors (such as processor 306) that can execute data in the form of computer-readable instructions to provide a functionality. Data, such as computer-readable instructions, can be stored on storage, such as storage/memory 308, that can be internal or external to the computer. The storage can include any one or more of volatile or non-volatile memory, hard drives, flash storage devices, and/or optical storage devices (e.g., CDs, DVDs, etc.), among others. As used herein, the term “computer-readable media” can include signals. In contrast, the term “computer-readable storage media” excludes signals. Computer-readable storage medium/media includes “computer-readable storage devices.” Examples of computer-readable storage devices include volatile storage media, such as RAM, and non-volatile storage media, such as hard drives, optical discs, and flash memory, among others.

Examples of devices can include traditional computing devices, such as servers, personal computers, desktop computers, notebook computers, cell phones, smart phones, personal digital assistants, pad or tablet type computers, mobile devices, wireless devices, cameras, routers, or any of a myriad of ever-evolving or yet to be developed types of computing devices. A mobile computer or mobile device can be any type of computing device that is readily transported by a user and may have a self-contained power source (e.g., battery). Similarly, a wireless device can be any type of computing device that has some capability to communicate with other devices without being physically connected to them.

In the illustrated implementation, devices 302 are configured with a general purpose processor 306 and storage/memory 308. In some configurations, a device can include a system on a chip (SOC) type design. In such a case, functionality provided by the device can be integrated on a single SOC or multiple coupled SOCs. One or more processors can be configured to coordinate with shared resources, such as memory, storage, etc., and/or one or more dedicated resources, such as hardware blocks configured to perform certain specific functionality. Thus, the term “processor” as used herein can also refer to central processing units (CPUs), graphical processing units (CPUs), controllers, microcontrollers, processor cores, or other types of processing devices suitable for implementation both in conventional computing architectures as well as SOC designs.

Note that some implementations can utilize information about a device, such as location information. Any such information gathering can be conducted in a manner that protects the security and privacy of the user. The user can be given notice of the use and allowed to opt-in, opt-out, and/or define such use. In any event, the present implementations can be accomplished in a manner that utilizes the information in a very targeted manner that limits the use of the information to accomplishing the present task completion concepts.

In some configurations, individual devices 302 can have a fully functional or stand-alone task completion component 310. For instance, device 302(1) can have a task completion component 310(1) that includes cross-device task continuation predictor 204(1), proactive tool 206(1), and task synthesizer 208(1) such that device 302(1) can perform all of the functionality described relative to FIG. 2. In an alternative configuration, device 302(1) could include a less robust task completion component 310(1) that includes a cross-device task continuation predictor 204(1). In this latter case, the task completion component 310(1) may communicate predictions from the cross-device task continuation predictor 204(1) to another device, such as device 302(5). The device 302(5) could include a task completion component 310(5) that is configured to utilize the predictions to operate on the user's behalf in an instance where the user resumes the task at a subsequent point and/or on a subsequent device 302.

Still another configuration can be thought of as a server-based configuration. In that configuration, device 302(5) can include a robust task completion component 310(5). Device 302(5) can support user functionality that the user can access from other devices 302(1)-302(4). The other devices 302(1)-302(4) can operate as thin clients that the user interacts with. In such a configuration, the user interacts with individual devices 302(1)-302(4) but some or all of the processing can be performed on device 302(5). In such a configuration, the task completion component 310(5) can provide task completion features to the user that are available from whatever device (or devices) the user utilizes.

In summary, system 300 includes components that can save a user task, such as a search or a document from one scenario to a second scenario. The first scenario can involve the user interacting with a first device. The second scenario can involve the user interacting with a second device. For example, the user may start a search session on the first device and leave the first device without finishing the search session (e.g., without completing a desired task). The user can resume the search session on the second device. In another case, the first scenario can be time based. For example, the user may stop a search session on the first device in a first scenario. After a period of time the user may return to the first device in a second scenario to finish the search task. The search can be saved and/or acted upon for the user in the interim to provide a more satisfying experience compared to the user simply restarting the search in the second scenario. At the end of the first scenario the user may indicate that he/she intends to continue the search. In other cases, the user may not give any indication, but a prediction can be made whether the user will resume the search.

Note that for ease of explanation, a single task is often discussed in the examples, however, the user may engage in multiple tasks concurrently (e.g., have multiple unfinished tasks at the same time). Strategies for handling task completion can be adapted to individual tasks and as such different tasks may be handled differently. For instance, while the task examples described above can be accomplished relatively quickly (e.g., completing a search task) other tasks may be relatively long term such that the tasks (and/or sub-tasks thereof) extend for relatively long periods of time. For instance, a user task may relate to planning a wedding or buying a house. The user may work on such a task for weeks or months and/or make multiple transitions involving multiple devices.

FIGS. 4-6 collectively relate to a ‘multi-task’ task completion scenario. In this example starting at FIG. 4, assume that the user is working on notebook computing device 302(3). For purposes of explanation, assume that the user is working on two applications. In this case, the first application can be a search engine (e.g., web browser application) 402(1) and the second application can be a document application (e.g., spreadsheet application 402(2)). A first GUI 404(1) relates to the first application and the second GUI 404(2) relates to the second application. On the first GUI 404(1), the user is searching the query term “hit movies” as indicated at 406. Results are shown generally at 408. The first result (e.g., highest ranked result) is the movie “The Hit (1984)” as indicated at 410. The second result is the movie “The Hit (2007)” as indicated at 412. The third result is “Hit movies playing now” as indicated at 414. Assume for purposes of explanation that these are not the results that the user wants and as such the task remains unfinished (e.g., incomplete).

Relative to the spreadsheet application 402(2), the user is calculating “January travel costs” as indicated at 416. The user has entered several values as indicated generally at 418. However, at this point, the user has not completed either the search task or the document task and yet is logging off from the computing device 302(3) as indicated at 420. For instance, assume that the user has to leave work to catch the bus home.

FIG. 5 shows first and second instances involving computing device 302(1). Instance 1 shows the user successfully logging into the computing device (e.g., “password accepted” at 502).

At instance 2 the search engine (e.g., browser application) 402(1) is automatically presented to the user on GUI 504. Alternatively, the user can launch the search engine (e.g., launch web browser and search engine). In either case, the task completion component 310 (FIG. 3) has predicted that the user is likely to resume this task. Further, the task completion component has taken actions on behalf of the user to aid in task completion. In this case, the task completion component has determined that the user likely wanted to search “hit movies playing nearby”. As such, the task completion component has updated the search terms as indicated at 506 (compare designator 506 of FIG. 5 to designator 406 of FIG. 4). Accordingly, updated search results are indicated generally at 508 (compare designator 508 of FIG. 5 to designator 408 of FIG. 4). In this case, the highest ranking result is now “Northpoint Theater” with links to movies and times. The task completion component can take these actions on behalf of the user by learning from previous user actions as explained above relative to FIG. 2. The task completion component can also use information from the mobile devices, such as location and direction of travel. For instance, Northpoint Theater may be ranked higher than Lakeside Theater based upon the location and direction of travel of the user.

The task completion component 310 can also utilize other information, such as location information, day of the week information, time of day, etc. For instance, the user may have previously made similar searches on Friday evenings and the user may have started the present search on a Friday evening. Thus, the task completion component can make it much easier and simpler for the user to complete the search task and go to the movies. For example, the user can simply select “Northpoint Theater” to complete the task. In an alternative configuration, if the user's past history indicated that the user tends to purchase movie tickets online, the task completion component may progress into the Northpoint Theater website to present a “purchase tickets” link to the user to further reduce the actions that the user has to take to complete the task. In this case, the user did not have to enter any search terms on computing device 302(1) to complete the task. Thus, user convenience is enhanced in several ways, such as time and/or ease of input, among others.

FIG. 6 shows a subsequent time where the user is logged into his/her tablet computing device 302(2). For instance, the user may be using the tablet after the movies or the next day. In this case, task completion component 310 (FIG. 3) can predict that the user will resume the spreadsheet task on the tablet computing device. For instance, previous user actions can indicate that the user tends to resume search tasks on either his/her smart phone or tablet, but only tends to resume document tasks on the tablet. Such a scenario could occur where the user finds the display area and/or the input mechanisms of the smart phone to be satisfactory for search tasks, but inadequate for document tasks.

In this case, the task completion component 310 can predict that the user will resume the task on the tablet computing device 302(2) and take actions on behalf of the user to complete the task. In this example, the task completion component has utilized computing resources on behalf of the user in the intervening period between when the user stopped working on the task and when the user resumes the task. In this case, the spreadsheet application 402(2) includes the values 418 entered by the user on the notebook computing device 302(3) (FIG. 4). Further, the task completion component has utilized computing resources to calculate the total for the entries as indicated at 602. Thus, when the user resumes the spreadsheet task on the tablet computing device 302(2) actions have been taken to complete the task for the user (e.g., calculate the total). Of course, a relatively simple example is illustrated and discussed here for sake of brevity. The present concepts are applicable to more complex and/or different task completion scenarios.

To summarize, the present concepts can be applied to different types of tasks and/or across different types of computing devices in order to make task completion easier for the user.

Prediction Methods

As introduced above, the inventive concepts involve methods to learn accurate predictive models from data to predict contiguous task resumption across devices. Stated another way, the predictions can relate to the next task (or tasks) in the temporal sequence of user actions on his/her computing devices. Several implementations focus on contiguous tasks since those are resumed soon, affording the search engine the opportunity to help, rather than at some point in the next few days or week. Machine learning models can be utilized for these contiguous tasks. The machine learning models can use behavioral, topical, geospatial, and temporal features derived from data. One potential utility of these feature classes for the prediction task is determined by initial empirical analysis. Some models have strong predictive accuracy and can have direct implications for the development of tools to help people search more effectively in a multi-device world.

Data

The search activities of a user can be represented as a stream of temporally-ordered queries. Query streams can provide rich information about users' search interests and search tasks. In order to better capture the search intent of users, the concept of a search session can be employed to segment the query stream into fragmented units for analysis. Here, a typical search session can be defined using a 30-minute timeout to determine its boundaries in the stream. Of course, the 30 minute timeout value is provided for purposes of explanation. Other implementations could use other defined timeout values (e.g., defined time periods). For instance, timeout values from as short as a minute to more than an hour could be utilized.

A device switch can be defined as the act of moving between a pair of devices (e.g., personal computer→smartphone). In accordance with some implementations, a search session can consist of one or more queries, but this analysis does not permit a search session to span multiple devices. In other words, the queries within the same session occur on a single device. As a result, switching between devices involves at least two sessions, the pre-switch session and the post-switch session, in this implementation.

More precisely, let Q={q₁, q₂, . . . , q_(i), . . . , q_(n)} be the query stream of a user, where q_(i) is the i-th query in the stream. For each q_(i) (1≦i≦n), there is a 3-tuple (t_(i), s_(i), d_(i)) associated with it, where t_(i) is the timestamp of the query q_(i), s_(i) represents the session of q_(i), and d_(i) defines the device where q_(i) has been issued. S is the personal search history comprising user search activity from Q in the time period before s_(i). In this setting, cross-device search can be defined as follows:

DEFINITION: A cross-device search is represented as a 7-tuple,

-   -   (S, q_(i), q_(i+1), s_(i), s_(i+1), d_(i), d_(i+1)).

And in this implementation, the following conditions need to be satisfied: (1) q_(i) is the last query in session s_(i); (2) q_(i+1) is the first query in session s_(i+1); (3) d_(i) and d_(i+1) are two different devices.

The device-switching behavior can start at time t_(i) and ends at time t_(i+1). Define q_(i) as the pre-switch query, s_(i) as the pre-switch session, and s_(i+1) as the post-switch session. One of the tasks that can be solved involves predicting whether the search task of q_(i) will be resumed in the immediately-following post-switch session s_(i+1), referred to as a contiguous cross-device task. All the queries in s_(i+1) are defined as post-switch queries, and q_(i+1) is the first query in the post-switch session. The following discussion shows that q_(i+1) is most likely to be related to continuing the task of q_(i) among all queries in the post-switch session. As previously defined, device-switching behavior can reveal very rich information about the user, including the individual device preferences for searching, the timespan and changing geo-location during the switch, and/or other switch-related session information.

Some implementations can focus on the switching between two devices. For instance, the first device can be a personal computer (PC) also referred to as “desktop” (note: the definition of desktops may also include laptops), and the mobile computing device (e.g., smart phone). To understand cross-device behavior, queries issued on both devices can be collected. Queries can be mined from the logs of both modalities separately and then joined using a persistent user identifier. For each query, its timestamp and geolocation can be recorded, allowing for temporal and geospatial characteristics to be studied.

Generating Features from Data

Given the behavioral data described in the previous section, aspects of the data can be mined corresponding to the following four characteristics, among others.

Behavioral: This aspect relates to the queries that users submit and their search behavior generally (e.g., number of search sessions), including their between device behavior (e.g., number of prior switches). Table 2 provides a more complete list of behavioral features. Note that although this discussion focuses on search queries, it is also possible to focus on the web pages and domains that users visit as an additional source of information for feature analysis.

Temporal: This aspect relates to the duration of the switch (the time between the pre- and post-switch queries) as well as when in the day switches tend to occur and the relationship between time-of-day and duration.

Geospatial: This aspect relates to the fact that one of the most common reasons for users to search on mobile is the limited mobility of desktop. One theory is that cross-device search may involve a change in location. In the analyzed dataset, geospatial information is available at city level (e.g., Seattle, Wash.) based on the same information from the internet providers on desktop and on the mobile device. Geospatial properties of the switching event (such as average speed during the switch) may help predict contiguous cross-device search tasks.

Topical: This aspect can be used to capture the users' search intent and construct models of their search tasks. This aspect can indicate how post-switch queries are affected by the topic of the pre-switch query. To do so, the sustainability of query topics can be analyzed during device switching.

Prediction Task

As stated earlier, a cross-device search can be defined by a 7-tuple, including the personal search history S, the pre-switch and post-switch queries q_(i) and q_(i+1), the pre-switch and post-switch sessions s_(i) and s_(i+1), and the devices used before and after the switch. Since the present detailed explanation focuses on the desktop-to-mobile switches, the definition could be simplified by excluding the device components.

Given a cross-device search, the implementations can predict whether the task of query q_(i) is continued by any of the queries in the post-switch session s_(i+1). Suppose the following Boolean function f can tell if two queries belong to the same task:

${f\left( {q_{m},q_{n}} \right)} = \left\{ \begin{matrix} {True} & {{{if}\mspace{14mu} q_{m}\mspace{14mu} {and}\mspace{14mu} q_{n}\mspace{14mu} {belong}\mspace{14mu} {to}\mspace{14mu} {the}\mspace{14mu} {same}\mspace{14mu} {task}},} \\ {False} & {{else},} \end{matrix} \right.$

Then the ground truth for the prediction will be:

V _(q) _(j) _(εs) _(s+1) f(q _(i) ,q _(j))  (1)

Again, q_(i) is the pre-switch query and s_(i+1) is the post-switch session. By comparing q_(i) with every query q_(j) in the post-switch session and taking the OR operation with the results, the final ground truth for the cross-device search (S, q_(i), q_(i+1), s_(i), s_(i+1)) can be obtained. One prediction task can therefore be to predict the result of function (1) using features extracted from (S, q_(i), q_(i+1), s_(i), s_(i+1)).

The Choice of Function f

Function f measures the relevance between two queries in terms of searching tasks. One option is to ask human labelers to determine the relevance for every query pair. However, this approach may not be feasible for large-scale data.

In order to obtain the ground truth for all cross-device searches in the test dataset, this explanation can use a lightweight function f. Initially, randomly chosen pre- and post-switch query pairs can be manually labeled. A Support Vector Machine (SVM) classifier can be trained using the manual labels and features listed in table 1:

TABLE 1 Name Description EditDistance Editing distance between two queries NumTermOverlap Number of overlapping terms in two queries QueryTermJaccard Jaccard coefficient of two query term sets IsSameQuery Boolean, true if two queries are identical IsSubsetQuery Boolean, true if one query contains the other

The trained SVM classifier can be used as function f. Five-fold cross-validation on function f against the human judgments can show that f is very accurate on the positive class and it can capture two thirds of related-query pairs.

Features

The device-switching process can be temporally segmented into five stages and design features accordingly. These five stages include: (1) User's searching history S; (2) Pre-switch session s_(i); (3) Pre-switch query q_(i); (4) The transition, time period from t_(i) to t_(i+1); (5) Post-switch session s_(i+1). Table 2 lists examples of features for each stage.

TABLE 2 Name Description Features from Search History S NumOfDesktopQuery Number of queries issued on desktop NumOfMobileQuery Number of queries issued on mobile PercentageDesktopQuery Percentage of queries issued on desktop PercentageMobileQuery Percentage of queries issued on mobile PercentageDesktopTime Percentage of searching time on desktop PercentageMobileTime Percentage of searching time on mobile NumOfSession Number of search sessions NumOfContiguousSwitch Number of contiguous cross-device search tasks NumOfRelevantCrossDevice Number of search tasks appearing on both devices EntropyAvg Average device entropy of same-task queries EntropySum Total device entropy of same-task queries EntropyWeighted Weighted device entropy of same-task queries Features from Pre-switch Session s_(i) NumOfQuery Number of queries within session s_(i) TimeSpanPreSess Temporal length of session s_(i) (in minutes) NumOfLocationQuery Number of location-related queries in session s_(i) AvgDistancePreSession Average distance from current location to locations mentioned in session s_(i) Features from Pre-switch Query q_(i) GlobalFrequency The historical frequency of q_(i) in the entire dataset PersonalFrequency The frequency of q_(i) in personal search history S NumExactQueryDesktop Number of same queries as q_(i) on desktop in S NumExactQueryMobile Number of same queries as q_(i) on mobile NumRelatedQueryDesktop Number of related queries as q_(i) on desktop NumRelatedQueryMobile Number of related queries as q_(i) on mobile NumExactQuerySwitch Number of switches that pre-switch query and post-switch query are the same as q_(i) NumRelatedQuerySwitch Number of switches that pre-switch query and post-switch query are both relevant to q_(i) PreQueryContiguousSwitch Number of contiguous cross-device tasks of q_(i) NumOfRelatedQueryInSession Number of queries relevant to q_(i) in session s_(i) NumOfTerm Number of terms in query q_(i) PreQueryCategory The search topic of query q_(i) PreQueryHour The hour component of t_(i) PreQueryDayofWeek The day of week of t_(i) IsWeekday Boolean, indicates t_(i) is weekday or weekend HasLocation Boolean, true if q_(i) contains location PreQueryDistance The distance from current location to location in q_(i) HasLocalService Boolean, true if q_(i) contains local service Features from the Transition (t_(i)~t_(i+1)) TimeIntervalSwitch The timespan between t_(i) and t_(i+1) GeoDistanceSwitch The distance between where q_(i) and q_(i+1) are issued IsSameLocationSwitch Boolean, true if q_(i) and q_(i+1) occur at the same place AvgSpeedSwitch Average travelling speed during the switch Features from Post-switch Session s_(i+1) TimeSpanPostSession The temporal length of session s_(i+1) PostQueryCategory The search topic of query q_(i+1) PostQueryHour The hour component of t_(i+1) GeoDistancePostSession The distance travelled within session s_(i+1) AvgSpeedPostSess Average travelling speed within session s_(i+1)

Function f can be used to group queries into search tasks: Since function f is designed to judge the relevance of query pairs, f can be applied to every pair of queries in user's search history, and then cluster queries into groups. Each group of queries can represent a certain search task. By observing how the group of queries distributes on desktop and mobile, it is possible to compute entropy-based features and cross-device features.

Suppose G_(i) is the i-th group in the user's search history, and it consists of k queries, G_(i)={q_(i) ₁ , q_(i) ₂ , . . . , q_(i) _(k) }. Among these k queries, l of them are issued on desktop and (k−l) queries are on mobile. Then the device entropy of G_(i) is:

${\frac{1}{k}\log \frac{k}{1}} + {\frac{k - 1}{k}\log \frac{k}{k - 1}}$

Not only entropy-based features are computed from query groups, some other cross-device-related features are also computed by grouping queries into search tasks first. The purpose is to capture the individual device preferences for different tasks. For example, the history feature NumOfRelevantCrossDevice counts the number of tasks spanning both devices; the pre-switch query feature NumRelatedQuerySwitch counts the number of contiguous cross-device searches on the tasks of q_(i).

Training the Model

As mentioned above, the predictive model can be trained with labeled data. Labels for the prediction task can be obtained in two ways: automatic labeling and annotation by human labelers.

Automatic Labelling

Automatic task labeling can be applied to obtain labels for all the cross-device searches in a dataset. As mentioned above function f can be used to annotate the data.

Human Labeling

In some cases, human annotators can be utilized to label the cross-device searches in the dataset. For instance, given recent search history, the pre-switch query, and the post-switch session, human annotators can be asked to label every query in the post-switch session if it belongs to the same search task as the pre-switch query.

Applying the Model

The present concepts can support searchers performing cross-device searching at different points in the switch. As mentioned earlier, two points of interest can be defined as: (1) immediately following the session on the pre-switch device, and (2) on visiting the search engine homepage on the post-switch device.

Immediately Following Pre-switch Session

Accurately predicting future task resumption at this point means that the search engine can perform actions on the users' behalf to (potentially) maximize the downtime between task termination and resumption. Examples of actions the search engine could do during this time are described above and below.

A first example of an action that can be taken before task resumption can include proactively saving recent session state into cloud server memory or disk cache for rapid access when the task is resumed. Tasks could be resumed via the search engine homepage or from any search engine result page. Recall that this aspect was described above relative to FIG. 2. In that discussion, search state from pre-switch sessions 236, Search interactions, queries and SERP clicks 220 and/or results 224 could be saved at 246.

A second example action can include trying different ranking algorithms that may be less efficient but more effective, or issue multiple related queries and blend or summarize the results. The search engine could also re-run recent abandoned queries, favoring quality over speed. Better quality results could be made available to searchers via alerts while mobile or via a link on the search engine homepage. Recall that in the discussion of FIG. 2, these actions can be accomplished by the proactive tool 206 and/or the task synthesizer 208.

Another example action can be starting a reconnaissance agent to proactively retrieve content from the Web that pertains to the user's current task. This new content could be made available to searchers via alerts while mobile or via a link on the search engine homepage, or any other viable means.

Still another example action could be posing the query to a question answering site such as Yahoo! Answers® (answers.yahoo.com), if the query is sufficiently descriptive to be posed as a question. If the user's intent is not sufficiently described, the search engine could prompt the user prior to departing the search engine on the pre-switch device to provide more information about their needs, perhaps even phrased as a natural language question for posting to community question-answering sites, social networks, etc. Recall that relative to the discussion of FIG. 2, these aspects can be accomplished by the proactive tool 206.

The predictive models can be valuable here because many of these actions are resource intensive and it can be advantageous from a resource perspective to not perform the actions for all queries. One alternative to the prediction is to provide users with a way to tell the system that they will resume soon. This can require an additional action from users, which they may forget or be unwilling to perform, and it may not always be clear to the user at termination time that resumption is likely. A combination of such a capability plus prediction may be beneficial to the user.

A further action example can involve a visit to a search engine homepage on the post-switch device by the user. The act of the user visiting the homepage can provide access to features about the transition between devices that can be useful in the task continuation prediction. Examples of support actions are described below.

One example of a supporting action at this point can be providing the user with the option to explicitly resume their task. Clicking on that option on the homepage would restore their state to that before the switch occurred, including marking pre-switch clicked result hyperlinks as visited and populating the recent query history with pre-switch queries.

Another supporting action can involve populating pre-switch queries in auto-completion drop-downs or automatically populate the search box on the homepage. Given that users have been observed to experience difficulty with typing on mobile devices, such support may speed up query entry.

Some implementations could also provide support on the basis of the queries on the post-switch device. This strategy could lead to even more accurate task-continuation prediction. Extending a mobile search session back to the immediately-preceding desktop session may help address the “cold start” problem of insufficient context to personalize early queries on mobile devices.

Beyond Prediction: Explicitly Indicating Task Resumption

Predictive models can reduce the burden on the user, but they can also be unreliable in some cases. An additional aspect that can be addressed involves searchers explicitly indicating to the search engine that they are going to resume the current search task on the post-switch device. This would serve as a reliable cue for the search engine to perform actions such as those described in the preceding section above. This could be implemented in the form of a “be right back” button displayed on the search engine homepage or any of the result pages. Additionally, the search engine could provide an option (button, link, etc.) on the homepage or any other search engine page on the post-switch device for searchers to explicitly indicate that they are resuming their pre-switch task. When selected, this would enable actions such as those described in the “On Visit to Search Engine Homepage on Post-Switch” section above.

Other Devices and Switching Directions

Note that although much of the discussion focuses on switches from desktop PCs to smartphones in this analysis, the concepts can be applied to any task resumption scenario relating to one or more devices. Switches can be in any direction between any two devices (laptops, tablets, slates, smartphones, e-readers, desktop PCs, etc.) and could even involve more than just device pairs if appropriate chaining is identified (e.g., a student could use a slate to take notes in class, a desktop PC to work on the assignment based on the notes, and a smartphone to converse with collaborators on the assignment and edit the document on the go).

The discussion above goes into substantial detail regarding specific implementations. Stepping back, the following methods convey some of the inventive concepts in a broader sense.

FIG. 7 shows a method 700 for facilitating task completion.

The method can identify that a user is working on a task on a computing device associated with the user at 702. For instance, the user may be logged into the computer. The user can be performing the task on an application. The application can be stored on the device and running on the device. Alternatively, the application can be running remotely and presented on the computing device as a graphical user interface.

In some cases the user may stop working on the task without completing it. In such an instance when the user stops using the computing device without completing the task, the method can predict a likelihood that the user will subsequently resume the task on another (e.g., second) computing device associated with the user at 704. In some cases, the prediction can include detecting that the user logged-off of the computing device without completing the task. Such an occurrence can be an indicator that the user is likely to resume the task. In other cases, the prediction can include detecting continued use of the computing device by the user for other tasks after the user stops working on the task without completing the task. Such an occurrence can be an indicator that the user is not likely to resume the task.

In an instance where the likelihood exceeds a threshold the method can attempt to aid the user in completing the task on the second computing device at 706. The threshold can be an absolute threshold such that the threshold value is 1. Alternatively, the threshold can be a lower value, such as 0.75 for example. The method can attempt to aid the user in various ways. For instance, the method can automatically populate the task onto the second computing device. In cases where the task is a search task, the method can refine results of the search task prior to the user resuming the search task. The method can consider user interaction during previous user tasks to determine how to aid the user. For example, the attempting to aid can entail utilizing one or more computing resources on behalf of the user prior to the user resuming the task on the second computing device. Such configurations can allow time consuming activities to be performed for the user. The results of the time consuming activities can be presented when the user resumes the search. For example, the method could present the task to a human expert. Results received from the human expert could be presented to the user or utilized to further refine the task on behalf of the user.

FIG. 8 shows a method 800 for facilitating task completion.

In some instances a user can be working on a task on a computing device associated with the user. The user may stop using the computing device without completing the task. In such a case, the method can predict that the user will subsequently resume the task on a second computing device associated with the user at 802.

The method can cause the task to be automatically presented to the user on the second computing device at 804.

The method can next predict actions that the user will take to complete the task at 806. The next or second prediction can be based upon user interactions on prior tasks.

The method can take individual actions on behalf of the user to assist the user in completing the task at 808. Thus, the method can aid the user in completing the task in a manner that is faster, easier, and/or more performant than would otherwise be the case.

The order in which the example methods are described is not intended to be construed as a limitation, and any number of the described blocks or acts can be combined in any order to implement the methods, or alternate methods. Furthermore, the methods can be implemented in any suitable hardware, software, firmware, or combination thereof, such that a computing device can implement the method. In one case, the method is stored on one or more computer-readable storage media as a set of instructions such that execution by a processor of a computing device causes the computing device to perform the method.

CONCLUSION

Although techniques, methods, devices, systems, etc., pertaining to task completion are described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claimed methods, devices, systems, etc. 

1. One or more computer-readable storage media storing computer-readable instructions that when executed by a processor cause the processor to perform a method, comprising: identifying that a user is working on a task on a computing device associated with the user; predicting a likelihood that the user will subsequently resume the task on another computing device associated with the user; and, in an instance where the likelihood exceeds a threshold, attempting to aid the user in completing the task on the another computing device.
 2. The one or more computer-readable storage media of claim 1, wherein the predicting comprises detecting that the user logged-off of the computing device without completing the task or the user stopped using the computing device for a defined time period.
 3. The one or more computer-readable storage media of claim 1, wherein the predicting comprises detecting whether the user worked on any other tasks after the user stopped working on the task without completing the task.
 4. The one or more computer-readable storage media of claim 1, wherein the attempting to aid comprises automatically populating the task onto the another computing device.
 5. The one or more computer-readable storage media of claim 1, wherein in an instance where the task comprises a search task, the attempting to aid comprises refining results of the search task prior to the user resuming the search task.
 6. The one or more computer-readable storage media of claim 1, wherein in an instance where the task comprises a search task, the attempting to aid comprises considering user interaction during previous user tasks.
 7. The one or more computer-readable storage media of claim 1, wherein the attempting to aid comprises utilizing one or more computing resources on behalf of the user prior to the user resuming the task on the another computing device.
 8. A method, comprising: in an instance when a user is working on a task on a computing device associated with the user, making a first prediction that the user will subsequently resume the task on another computing device associated with the user; causing the task to be automatically presented to the user on the another computing device; making a second prediction relating to actions that the user will take to complete the task, wherein the second prediction is based upon user interactions on prior tasks; and, taking individual actions on behalf of the user to assist the user in completing the task.
 9. The method of claim 8, wherein the instance occurs when the user logs off of the computing device without completing the task or wherein the instance occurs when the task remains unfinished for a period of time.
 10. The method of claim 8, wherein the task relates to an application and wherein the automatically presenting comprises opening the application on the another computing device and automatically populating content in the application on the another computing device.
 11. The method of claim 8, wherein the making a first prediction is performed only when a determination is made that the user has stopped using the computing device without completing the task.
 12. The method of claim 8, further comprising making a third prediction that the user will subsequently resume the task on still another computing device associated with the user.
 13. The method of claim 12, further comprising making a fourth prediction relating to further actions that the user will take to complete the task.
 14. The method of claim 8, wherein the second prediction is based upon user actions relating to other tasks in previous interactions with the computing device and the another computing device.
 15. The method of claim 8, wherein the second prediction is based upon capabilities of the computing device and the another computing device.
 16. The method of claim 15, wherein the capabilities relate to display area of the computing device and the another computing device or wherein the capabilities relate to input devices of the computing device and the another computing device.
 17. The method of claim 15, wherein the taking individual actions occurs before the user resumes the task on the another computing device, and the method further comprises taking further additional actions after the user resumes the task on the another computing device.
 18. The method of claim 15 performed by a server computer that is different from the computing device and the another computing device.
 19. A device, comprising: memory and a processor configured to execute instructions stored on the memory; a display upon which a user can interact with the device on a task; and, a task prediction component configured to generate a prediction whether the user intends to resume the task at a subsequent point in time, the task prediction component configured to communicate the prediction to a task completion service that can facilitate the user completing the task.
 20. The device of claim 19, wherein the task prediction component is configured to record user interactions during the task and to send the user interactions to a task completion service. 